Set Interface

Use Set Interface to set the OSPF parameters for the router's network interfaces.

  1. Enter the interface IP address for each interface in the router.

    Select the Submit button.

  2. Enter the attaches to area.

    This is the area the interface attaches.

  3. Enter timer values. You should enter the same values for all routers attached to a common network segment.

    1. Enter the retransmission interval.

      Retransmission Interval is the interval after which a Link Request for one or more link state advertisements will be re-sent.

    2. Enter the Transmission delay.

      This parameter is an estimate of the number of seconds that it takes to transmit link-state information over the interface.

      Each link-state advertisement has a finite lifetime that is equal to the constant MaxAge (1 hour). As each link-state advertisement is sent to the particular interfaces, it is aged by this configured transmission delay. The minimum delay is 1 second.

      Valid Values: 1 to 65535 seconds

      Default Value: 1

    3. Enter the Router Priority.

      This value is used for broadcast and non-broadcast multiaccess networks to elect the designated router. For point-to-point links, this value should be 0, which means that this router must not be elected the designated router for its network.

      Valid Values: 0 to 255

      Default Value: 1

    4. Enter the Hello Interval.

      Hello Interval is the interval between hello packets sent on the interface.

      Valid Values: 0 to 255 seconds

      Default Value: 30

    5. Enter the Dead Router Interval.

      Dead Router Interval is the interval after which a router that has not sent a hello will be considered dead.

      Valid Values: 1 to 65535 seconds

      Default Value: 40

  4. Enter the Type of service 0 cost.

  5. Enter the Authentication key.

    This parameter defines the password used for this OSPF area. When password authentication is used, only packets with the correct authentication key are accepted.

    Valid Values: any 8 characters

    Default Value: 0

  6. Retype the authentication key.

Select the Submit button.


Set Non-Broadcast Network Description

For Frame Relay, X.25, or ATM networks selecting Set Non-Broadcast is used to configure an OSPF interface as connecting to a non-broadcast multi-access network. If Set Non-Broadcast is not used, the interface is assumed to be connected to a point-to-multipoint network. In Frame Relay networks, all OSPF interfaces must be configured as connecting to the same type of network (non-broadcast multi-access or point-to-multipoint), so if the Set Non-Broadcast is used for one interface, it must be used for all interfaces on the network.

  1. Enter the interface IP address.

    Valid Values: any valid IP address

    Default Value: none

  2. Select the Submit button.

  3. Enter the Poll interval.

    Description

    This parameter sets the interval in which OSPF packets are sent to a neighbor that is inactive.

    Valid Values: 1 to 65535 seconds

    Default Value: 120

Select the Submit button.


Set Virtual Link

Virtual links can be configured through a non-backbone area to establish and maintain connectivity of the backbone of the Autonomous System.

Virtual links connect physically separate components of the backbone. The two endpoints of a virtual link are area border routers. The virtual link must be configured in both routers. OSPF supports virtual links to extend the backbone area's connectivity through a transit area.

The virtual link is treated as if it were an unnumbered point-to-point network and the two end-points of the virtual link were Area Border Routers (ABRs).

Use Set Virtual Link to configure virtual links between any two area border routers. To maintain backbone connectivity you must have all of your backbone routers interconnected either by permanent or virtual links. Virtual links are considered to be separate router interfaces connecting to the backbone area.

Virtual links can be configured between any two backbone routers that have an interface to a common non-backbone area. Virtual links are used to maintain backbone connectivity and must be configured at both endpoints.

  1. Enter the virtual endpoint (router ID) that defines the ID of the virtual neighbor.

    Valid Values: any valid IP address

    Default Value: none

  2. Enter the link's transit area.

    This is the non-backbone, non-stub area through which the virtual link is configured. Virtual links can be configured between any two area border routers that have an interface to a common non-backbone and non-stub area. Virtual links must be configured in each of the link's two endpoints.

    Valid Values: 0.0.0.1 to 255.255.255.255

    Default Value: 0.0.0.1

  3. Click on Submit.

  4. Enter timer values. You should enter the same values for all routers attached to a common network segment.

    1. Enter the retransmission interval.

      Retransmission Interval is the interval after which a Link Request for one or more link state advertisements will be re-sent.

    2. Enter the Transmission delay.

      This parameter is an estimate of the number of seconds that it takes to transmit link-state information over the interface.

      Each link-state advertisement has a finite lifetime that is equal to the constant MaxAge (1 hour). As each link-state advertisement is sent to the particular interfaces, it is aged by this configured transmission delay. The minimum delay is 1 second.

      Valid Values: 1 to 65535 seconds

      Default Value: 1

    3. Enter the Hello Interval.

      Hello Interval is the interval between hello packets sent on the interface.

      Valid Values: 0 to 255 seconds

      Default Value: 30

    4. Enter the Dead Router Interval.

      Dead Router Interval is the interval after which a router that has not sent a hello will be considered dead.

      Valid Values: 1 to 65535 seconds

      Default Value: 40

  5. Enter the Authentication key.

    This parameter defines the password used for this OSPF area. When password authentication is used, only packets with the correct authentication key are accepted.

Select the Submit button.


Add Community

Use this option to create a community. It will be created with a default access of read_trap, a view of all, all traps disabled and all IP addresses allowed.

Note: Add Community does not allows you to select access type or trap control. Use set community access to assign access types to existing SNMP communities and select Enable Trap or the Disable Trap for trap control.

Enter the community name.

This parameter provides a community name used by the SNMP client. This community name is used when accessing the management information base (MIB) in the device from the host specified by the Community IP address parameter.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Add Address

Use this option to add to the community definition an address of a network management station in the network that should be allowed to communicate with this box.

More than one address can be added to a community; select Add Address each time you want to add another address.

If you do not specify an address for a community, requests are handled from any host. Addresses specify hosts that receive the traps. If no address is specified, no trap is generated.

Also, a trap is sent to a specified host only if the associated net mask is defined as 255.255.255.255.

  1. Enter the community name.

    Valid Values: a string of 1 to 32 alphanumeric characters.

    Characters such as spaces, tabs, or key sequences are not supported.

    Default Value: none

  2. Enter the IP address

    Valid Values: any valid IP address

    Default Value: none

  3. You also may supply a net mask to restrict access to either an individual host (mask=255.255.255.255) or to a network of hosts.

    Valid Values: 0.0.0.0 - 255.255.255.255

    Default Value: none

Select the Submit button.


Add Sub_Tree

Use this option to add a portion of the MIB to a view or to create a new view. The default is the entire MIB. Add Sub_Tree is used to manage MIB views. More than one subtree can be added to a view defined by ªview_text_name³. To create a new MIB view, select Add Sub_Tree with the new view name.

Note: You must assign a view to one or more communities by selecting Set Community View to have it take effect. The subtree definitions are inclusive; that is, the subtree OID specified and any OID that is lexicographically greater than the specified OID is considered part of the MIB view.

  1. Enter a view name.

    This parameter allows you to select the view used by the community defined in the Community name parameter. This view determines which MIB objects this community may access. If no view is specified, the community may access all objects known to the router's SNMP agent.

    This parameter should be answered if you decide to restrict a community from accessing the entire MIB managed by the router's SNMP agent.

    You must configure the View name parameter and the MIB Subtree parameter before you can configure this parameter.

    Valid Values:

    Default Value: All

  2. Enter the MIB OID name. This parameter specifies the MIB Object ID for the sub_tree. This must be entered as a numeric value, not a symbolic value.

    This parameter contains a MIB subtree name included in the view defined with the View name parameter. All children of a specified MIB subtree are also included in the view.

    For example, to provide a view that would give access to the system group in MIB-II, specify 1.3.6.1.2.1.1.

    Valid Values:

    An object identifier in the form of ....., where:

    Default Value: None

Select the Submit button.


Delete Community

Use this option to remove a community and its IP addresses.

  1. Enter the community name.

    Valid Values: a string of 1 to 31 alphanumeric characters.

    Characters such as spaces, tabs, or key sequences are not supported.

    Default Value: public

    This parameter provides a community name used by the SNMP client. This community name is used when accessing the management information base (MIB) in the device from the host specified by the Community IP address parameter.

Select the Submit button.


Delete Address

This option removes an address from a community.

  1. Enter the community name.

    Valid Values: a string of 1 to 31 alphanumeric characters.

    Characters such as spaces, tabs, or key sequences are not supported.

    Default Value: public

    This parameter provides a community name used by the SNMP client. This community name is used when accessing the management information base (MIB) in the device from the host specified by the Community IP address parameter.

  2. Enter the IP address

    Valid Values: any valid IP address

    Default Value: none

  3. You also may supply a net mask to restrict access to either an individual host (mask=255.255.255.255) or to a network of hosts.

    Valid Values: 0.0.0.0 - 255.255.255.255

    Default Value: none

Select the Submit button.


Delete Sub_Tree

Use this option to remove a MIB or a portion of the MIB from a view.

  1. Enter a view name to be removed.

    This parameter allows you to select the view used by the community defined in the Community name parameter. This view determines which MIB objects this community may access. If no view is specified, the community may access all objects known to the router's SNMP agent.

    This parameter should be answered if you decide to restrict a community from accessing the entire MIB managed by the router's SNMP agent.

    You must configure the View name parameter and the MIB Subtree parameter before you can configure this parameter.

    Valid Values:

    Default Value: All

  2. Enter the MIB OID name. This parameter specifies the MIB Object ID for the sub_tree. This must be entered as a numeric value, not a symbolic value.

    This parameter contains a MIB subtree name included in the view defined with the View name parameter. All children of a specified MIB subtree are also included in the view.

    For example, to provide a view that would give access to the system group in MIB-II, specify 1.3.6.1.2.1.1.

    Valid Values:

    An object identifier in the form of ....., where:

    Default Value: None

Select the Submit button.


Set Community Access Read_Trap

Use this option to set read access and trap generation to the named community.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Set Community Access Write_Trap

Use this option to set write and read and trap generation access to the community specified.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Set Community Access Trap_Only

Use this option to indicate the community is used only when sending an SNMP trap.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Set Community View

Use this option to assign a MIB view to a community.

  1. Enter the community name.

    Valid Values: a string of 1 to 31 alphanumeric characters.

    Characters such as spaces, tabs, or key sequences are not supported.

    Default Value: public

  2. Enter the view name.

Select the Submit button.


Set Trap_Port

Use this option to specify a UDP port number, other than the default standard port 162, to send traps to.

Enter the UDP port.

The default is the standard port.

Select the Submit button.


Enable Trap All

Use this option to enable all traps in a specified community.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap Cold_Start

Use this option to enable cold start traps in a specified community. A cold start trap means that the transmitting router is reinitializing and that the agent's configuration or the protocol entity implementation may be altered.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap Warm_Start

Use this option to enable warm start traps in a specified community. A warm start trap means that the transmitting router is reinitializing, but the configuration or protocol implementation will remain the same.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap Link_Down

Use this option to enable link_down traps in a specified community. A link_down trap (2) recognizes a failure in one of the communication links represented in the agent's configuration. The link_down trap-PDU contains the name and value of the ifIndex instance for the affected link as the first element of its variable-bindings.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap Link_Up

Use this option to enable link_up traps in a specified community. A link_up trap recognizes that a previously inactive link in the network has come up. The link_up trap-PDU contains the name and value of the ifIndex instance for the affected link as the first element of its variable-bindings.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap Auth_Fail

Use this option to enable authentication failure traps for a specified community. Authentication failure traps indicate that the sender of the SNMP request does not have the proper permission to talk to this box's SNMP agent.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.


Enable Trap EGP

Use this option to enable EGP Neighbor Loss Traps in a specified community. EGP Neighbor Loss traps recognize that an EGP neighbor and peer has been marked down and is no longer a peer. The egpNeighborLoss trap-PDU contains the name and value of the egpNeighAddr instance for the affected neighbor as the first element of its variable-bindings.

Enter the community name.

Valid Values: a string of 1 to 31 alphanumeric characters.

Characters such as spaces, tabs, or key sequences are not supported.

Default Value: public

Select the Submit button.